Add mechanism to specify custom CSP in XPConnect Sandbox
Categories
(Core :: XPConnect, enhancement)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox134 | --- | fixed |
People
(Reporter: robwu, Assigned: robwu)
References
Details
(Whiteboard: [addons-jira])
Attachments
(1 file)
The XPConnect sandbox currently special-cases the behavior for Expanded principals containing an add-on principal, to set the default CSP of add-ons. This was added in bug 1581611. That implementation depends on the expanded principal containing an add-on principal, and it allows only one fixed CSP.
This implementation is too limited. For example, bug 1911835 introduces another use of a sandbox in extensions. Here, the principal is an Expanded principal consisting of just one content principal. Notably, there is no add-on principal there.
I'm going to add an option to customize the CSP. For now, It will only support expanded principals, since other principals are not needed yet, and supporting other principals requires more work (bug 1548468).
|
||
Updated•7 months ago
|
|
Assignee | |
Comment 1•7 months ago
|
||
|
||
Comment 3•7 months ago
|
||
| bugherder | ||
Description
•